Skip to content

fix(inference): discover Traex models and recover occupied proxy ports - #156

Merged
ScriptedAlchemy merged 1 commit into
mainfrom
codex/fix-provider-catalog-and-proxy-recovery
Nov 18, 2026
Merged

ScriptedAlchemy merged 1 commit into
mainfrom
codex/fix-provider-catalog-and-proxy-recovery

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

Traex could appear on an iPhone with the stock Codex models even when its endpoint was offline. Separately, a leftover CLIProxyAPI process could hold T3's saved port and keep returning HTTP 503 after a restart.

This change reads the model catalog from the actual Traex endpoint. A linked host with inference sharing enabled can advertise its own Traex bridge. A client authorized on both environments provisions a scoped grant once, after which the consumer can use the host without that client staying online. Reopening the picker refreshes availability. If every route is offline, Traex disappears. Saved chats keep their model history, and both clients block a model the endpoint no longer offers. iOS formats saved Codex model IDs for display.

The managed proxy starts on an available port with a configuration specific to the child process. This lets it recover without terminating the process that owns the old port.

The changed-file gate passed, including 605 tests and typechecking across 38 packages. Verified the picker on an iPhone 17 simulator with isolated direct and peer endpoints, including peer disconnect and reconnect. A request to the peer-only model completed through the consumer. The remote Mac was unavailable for a hardware test. Two real CLIProxyAPI processes also ran concurrently with separate management credentials.

Offline before Offline after
Traex incorrectly shows Codex models Only available providers appear

Direct Traex endpoint · Peer-only Traex endpoint

Implemented and verified with GPT-6 through Codex.

@changeset-bot

changeset-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3ef5eaf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ScriptedAlchemy
ScriptedAlchemy merged commit 1857cd2 into main Nov 18, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant